-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CloudSyncMgr] Renaming the CloudSyncMgr API according to functionality to add more APIs #483
Conversation
Signed-off-by: Nitu Gupta <[email protected]>
[Cloudsync] Added testcases to improve the Code coverage for MQTT
@@ -36,7 +36,7 @@ const ( | |||
type CloudSync interface { | |||
InitiateCloudSync(isCloudSet string) error | |||
//implemented by external REST API | |||
RequestCloudSyncConf(host string, clientID string, message mqttmgr.Message, topic string) string | |||
RequestCloudSyncPublish(host string, clientID string, message mqttmgr.Message, topic string) string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simply, what about Publish
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean just Publish(), I thought of this idea, but then thought would be confusing for nay neww developer to understand by just Publish and hence this name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
However this function is in the CloudSync. What about RequestPublish
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!!
0850f44
to
817c45d
Compare
Please correct |
817c45d
to
6154e42
Compare
Done!!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
@t25kim @MoonkiHong @tdrozdovsky PTAL 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please change
Please change: |
6154e42
to
70dc6ec
Compare
Done!! |
70dc6ec
to
e81e48a
Compare
…ublish Signed-off-by: Nitu Gupta <[email protected]>
e81e48a
to
0a93094
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Description
The APIs were names as per the naming convection followed for previous APIs as for example, APIV1Request<><<GET/POST>> But with multiple APIs being added going further in CloudSyncMgr it is necessary to modify the API in terms of functionality i.e publish, subscribe
Fixes # (#382 )
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
1.MQTT mosquitto broker is configured to be running in the AWS endpoint.
2. The edge orchestration is build and run using following command with option CLOUD_SYNC set to true
4.You should obtain the following message for successful publish
Same client sending data but connection is established only once.
Test Configuration:
Checklist: